home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Experimental BBS Explossion 3
/
Experimental BBS Explossion III.iso
/
virus
/
diskse24.zip
/
WARNING.NOT
< prev
Wrap
Text File
|
1993-12-28
|
4KB
|
79 lines
DiskSecure version 2.4, December, 1993
Copyright (C) by Padgett, all rights reserved
What's New
With version 2.4, DiskSecure II (DS II) becomes copyrighted
FreeWare (see DiskSec2.doc for details and restrictions) and
may be used by individuals without charge.
V2.4 adds redundant recovery of the DOS boot record to compensate
for a possibility of an attack by one of those viruses that
makes a "blind leap" onto the disk. I do not expect these to be
successful but just in case...
V2.4 also adds further checking on the part of the DS2CHK file to
detect tunnelling and disconnect attacks. It will also now generate
an error messsage each time it is run. This indicates proper operation.
DiskSecure
Though DS performs extensive error checking on itself and its
installation, one particular conflict should be noted: some
early Western Digital controllers (for XT class machines) using
the SUPERBIOS mode have the habit of writing 17 bytes to the Master
Boot Record (reported with 20 & 30 MB disks only) sometimes. Since
this does not occur on installation, DS installs normally
however, if the write should occur, DS will flag this change
with continual "MBR CHK" errors that persist despite recovery.
In this case, use of the recovery disk will be necessary. If
the procedure outlined in the README.DS file is followed, for
installation there will be no problem.
WD has been notified (1990) but as yet, no response has been
forthcoming.
Similar activity has been reported with an early ADAPTEC SCSI
controller on an ACER PC.
DiskSecure II
If using QEMM386 v7.0 or above and DOSDATA.SYS is in use (will be
in CONFIG.SYS), DS2MOVE.SYS should not execute before DOS_UP.SYS.
If DS2MOVE is *last* in CONFIG.SYS there should not be any problem.
DS2MOVE will not work if loaded "high". (DS2INST will automatically
put DS2MOVE.SYS last).
DS II will operate with any DOS version 2.10 or above but cannot
be installed or fully utilized with any version prior to 3.2.
(DS2BYP and DS2MOVE are not compatable with earlier OSs).
To install on a machine running an older OS, boot from a floppy
with a 3.2 or higher OS & run DS2INST.BAT).
When upgrading the operating system, particularly when a partial
installation is performed such as for MSDOS 6.0 => 6.2, DS II
should be removed before and re-installed after such upgrades.
Often the upgrade program is not smart enough to accomodate
the DS II write protection.
Infections
DiskSecure II has been made as nearly impregnable as possible
within the limitations of the IBM PC hardware specification,
However it is not perfect. If a PC boots from an infected disk
before DS II has gone resident (if you can set the CMOS to
always boot from C: you have the best protection possible with
software. If not SumFBoot or NoFBoot can protect atleast from
warm reboots) there is no way to prevent the infection from
occuring, at best DS II can immediately detect the infection
and, if not corrupted itself, remove the infection.
In a few cases (e.q. AZUSA) which causes direct corruption of
the MBR *the virus* will not be able to boot the disk far
enough for automatic disinfection to be invoked. Recovery then
must be accomplished by booting with the Recovery Floppy and
utilizing either the direct recovery file (DSPART.DAT renamed
to DSPART.COM and rexecuted) or by DISKSEC2.EXE. In either
case, not only the virus but also DS II will be removed and
reinstallation (using only DISKSEC2.EXE) will be necessary
to replace the DS II protection. This is necessary since
once corrupted, the DS II process should be replaced completely.